Some Microsoft Windows Server systems are categorized or can be installed as Server Core systems. They have no graphical user interface for management, and have some other limitations too.

QuickOPC does not support development work on Server Core systems, but you can run programs created with QuickOPC on them.

You should use the Production Installer (or your own installation method for the application your are creating) to install QuickOPC on the Server Core system. If you attempt to run the Full Installer on the Server Core, it will show a warning message. If you proceed with the installation using the Full Installer anyway, the product will install, and will work well for production purposes (runtime), but some features will not work. For example, no links installed by the Setup program will be functional, because they rely on the shell functionality that is not present in Server Core. No shortcuts are installed onto desktop, and to the Start menu (as there is no such thing on Server Core).

The Server Core systems are meant for programs with no graphical user interface. If you run a GUI program developed with QuickOPC on a Server Core system, it will most likely work - but that's not what the system was meant to be for. Ideally, your programs for Server Core should be services, Web apps, console applications, and such. There are also some limitations to what the GUI parts of QuickOPC can do on Server Core. For example:

• Launching a browser by clicking on a URL in the controls or dialogs provided by QuickOPC will not work.
• The ComputerBrowserDialog dialog (using Windows Shell) does not work.

'Support' means that QuickOPC is designed to work and tested on the environment, and vendor's technical support may be contacted for assistance with QuickOPC on the environment. Support may be not available for operating systems, .NET runtimes and other dependencies that are past their active lifecycle at the time of support request, even if they were supported at the time of product release.